TKTs Closed

- https://communify.atlassian.net/browse/TKT-2165 - Closed in favor of https://communify.atlassian.net/browse/DIP-13115 and set effective close date to May 5th 2025
    - Should investigate the 40x errors and if seem legit close and comment on it. Tiered can do this. Crucial to close as it prevents other tickets for DI DQ from spawning so we wouldn't know about outage
 
- https://communify.atlassian.net/browse/TKT-5278 - Closed and a RCA is underway in ticket https://communify.atlassian.net/browse/RCA-1301 - set effective close date as June 19th 2025

- https://communify.atlassian.net/browse/TKT-6112 - Sent back to T2 as they can handle the renewal - Sent back and handled the renewal...

- https://communify.atlassian.net/browse/TKT-5884 - Sent back to T2 as they can handle the renewal - Sent back and handled the renewal...

- https://communify.atlassian.net/browse/TKT-5215 - Could have been closed over a week ago based on comment from RBC saying its fine now. David reopened and assigned to me saying this 'Real Resolution Date' might not be for SLA so need to check with CIM

- https://communify.atlassian.net/browse/TKT-4423 - Created PJIRA Ticket https://communify.atlassian.net/browse/DIP-13130 to handle

- https://communify.atlassian.net/browse/TKT-6148 - Created PJIRA Ticket https://communify.atlassian.net/browse/DIP-13131 to handle

- https://communify.atlassian.net/browse/TKT-6146 - Created PJIRA Ticket https://communify.atlassian.net/browse/DIP-13130 to handle

- https://communify.atlassian.net/browse/TKT-5466 - Created PJIRA Ticket https://communify.atlassian.net/browse/DIP-13132 to handle






TKT Updated

 - https://communify.atlassian.net/browse/TKT-5543 - Screenshots need to be more contextual and less zoomed in. Found QIDs and asked Srini to look into it

 - https://communify.atlassian.net/browse/TKT-3417 - Need updated from Michael, Lance or Sean on this

 - https://communify.atlassian.net/browse/TKT-5082 - Srini to pick up Wed and create PJIRA ticket in favor of this ticket so we can close

 - https://communify.atlassian.net/browse/TKT-5549 - Ask srini about the QID Ambika mentioned and if we need to still have this ticket as its passing now
 
 - https://communify.atlassian.net/browse/TKT-5836 - Checked SSL Shopper and see that our services cert is valid and the DP URL cannot be found. Asked to check in with Vishnu periasami at RBC who does their certs

 - https://communify.atlassian.net/browse/TKT-5366 - Closing because I cannot understand the ask and need better documentation. Also lack of knowledge documented around WMApi and how to check apis in swagger - https://www.rbcinsight.com/WMApi/docs#/CompanyAPI/get_WMApi_company__wsodCompany_ - Last to have knowledge of this was Hiral

- 


PJira Tickets In Favor of TKT needing fields updated
- https://communify.atlassian.net/browse/DIP-13115
- https://communify.atlassian.net/browse/DIP-13134
- https://communify.atlassian.net/browse/DIP-13132
- https://communify.atlassian.net/browse/DIP-13130
- https://communify.atlassian.net/browse/DIP-13131


Things to do:
- Srini to help with WMAPI 
- Create a PJira for TKT-6148 for increase CPU to 300 for both CTC and PTC to accommodate high usage averages - https://communify.atlassian.net/browse/DIP-13131
- Create a PJira for TKT-6146 to increase container size from default 3 to 5 and reduce memory from 200 to 120 - https://communify.atlassian.net/browse/DIP-13130
- Create a PJIRA for TKT-5466 to increase CPU to 250 for both CTC and PTC to accommodate high usage averages - https://communify.atlassian.net/browse/DIP-13132
- Create a PJIRA for TKT-5782 - To increase the number of containers to 5 from 3 to accomidate high usage averages - https://communify.atlassian.net/browse/DIP-13134
- Create a PJIRA ticket for TKT-5725
